Repository navigation
Conversation
satorg
force-pushed
the
scalafmt-docstrings
branch
from
March 9, 2026 04:30
54c1555 to
7691397
Compare
satorg
force-pushed
the
scalafmt-docstrings
branch
from
March 22, 2026 22:57
7691397 to
77d1208
Compare
satorg
force-pushed
the
scalafmt-docstrings
branch
from
April 20, 2026 04:56
77d1208 to
8e82f5b
Compare
satorg
force-pushed
the
scalafmt-docstrings
branch
from
May 14, 2026 21:40
8e82f5b to
151c17e
Compare
satorg
force-pushed
the
scalafmt-docstrings
branch
2 times, most recently
from
September 22, 2026 22:12
57b489a to
20c54d1
Compare
satorg
force-pushed
the
scalafmt-docstrings
branch
from
November 7, 2026 02:46
20c54d1 to
24d4b16
Compare
Restore sentence boundaries that were lost when scalafmt reflowed
docstrings, keep inline code spans and links on a single line, put
equations and code samples back into {{{ }}} blocks, and align the
@example formatting in syntax/either.scala with ApplicativeError.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The only significant change is in
.scalafmt.conf:After that,
sbt prePRwas applied.Some manual fixes in Scaladoc were also necessary – not because Scalafmt "broke" something, but because a few existing Scaladocs were incorrectly formatted and were therefore treated as plain text. For example:
Details
A table defined in plain text like that:
had to be enclosed into
{{{ }}}in order to make a pre-formatted text. Otherwise, it turns into a mess.Why this change?
Two reasons:
Why this particular style?
docstrings.style = Asteriskaligns best with the majority of existing Scaladocs in the repository.UPDATE: this legacy setting was also removed from
.scalafmt.conf:It has no effect because the following
overrides it.